Fix m365d/mde hunting query options #702
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
update to latest
updates to latest
ianhelle
approved these changes
Sep 5, 2023
|
Hi, @ianhelle The CI test finally seemed to be approved. Thanks in advance. :) |
ianhelle
approved these changes
Sep 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
The start and end params are never used in all of m365d and mde hunting queries.
On the other hands, help messages of those queries imply they are available.
Thus, I made a PR to comment out.
In addition, I found one place to be fixed that the time_column is not reflected to min_Timestamp.
Thank you.
Best regards